Thank you for the initiative 🙌

But the design of this PR is bad:

1. We probably shouldn't require the user to have xnview installed to use previews on Windows.
2. We shouldn't hardcode the path to xnview.
3. We shouldn't open result images in xnview by default.

A better version of this PR could be:

• no changes to rclip code
• a change to README.md showing how to use xnview together with rclip to view files

Another option may involve building a generic adapter/helper that may try calling an image viewer if the user passed a CLI arg to ask for this, but this is more involved, and I am not sure if we need to do it now. But happy to discuss different approach ideas.

Can you change this PR to:

• remove changes to the rclip code
• add an example on how to use rclip with xnview, similar to this one:

  rclip/README.md

  Lines 121 to 137 in 01801ea

  	<details>
  	<summary>Using a different terminal or viewer</summary>
  	If you are using any other terminal or want to view the results in your viewer of choice, you can pass the output of **rclip** to it. For example, on Linux, the command from below will open top-5 results for "kitty" in your default image viewer:
  	```bash
  	rclip -f -t 5 kitty | xargs -d '\n' -n 1 xdg-open
  	```
  	The `-f` param or `--filepath-only` makes **rclip** print the file paths only, without scores or the header, which makes it ideal to use together with a custom viewer as in the example.
  	I prefer to use **feh**'s thumbnail mode to preview multiple results:
  	```bash
  	rclip -f -t 5 kitty | feh -f - -t
  	```
  	</details>

Thank you, and let me know if you have any questions 😄